Database Auditing |
|
Changes made to the database need to be tracked for future reference. Database auditing helps store changes made to the database in the form of an Audit Table, by generating methods on the table as defined by the Administrator. You can generate certain default methods for the audit table using the Method Set Generator. These include methods that indicate the insertions, deletions, and updates done on the database. Apart from these, if any specific querying needs to be run on the Audit Table, custom methods can be built and these can be used to view the changes made to the database.
The WS-AppServer connector is equipped with a facility to audit databases. The Administrator can define the audit configuration details, which are stored in the LDAP along with the Service details. After defining the audit configuration, the administrator can either enable or disable the auditing feature.
Features of Database Auditing:
- Provides a log of all changes made to the database over a period of time. Since the auditing feature is enabled by the WS-AppServer connector, all requests being processed by the Service get audited.
- The name of the Cordys user who made the changes will be available as part of the auditing information.
- You can only audit changes made through the Service (through the Process Platform framework). Any changes made directly to the database tables will not be reflected.